home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 21
/
Cream of the Crop 21 (Terry Blount) (October 1996).iso
/
os2
/
ircdor14.zip
/
ircdoor.doc
< prev
next >
Wrap
Text File
|
1996-08-15
|
35KB
|
841 lines
IRCDOOR 1.4 Manual
Copyright (c) 1996 by Andrew Eigus
Table of Contents
1. ...Introduction
2. ...Software and Hardware requirements
3. ...License agreement
4. ...Disclaimer
5. ...Installation instructions
6. ...IRC commands supported by IRCDOOR/2
7. ...IRCDOOR/2-specific commands
8. ...Comments
9. ...Registration information
10. ...IRCDOOR/2 distribution information
11. ...Contact information
1. Introduction
What is IRC?
IRC stands for "Internet Relay Chat". It was originally
written by Jarkko Oikarinen (jto@tolsun.oulu.fi) in 1988.
Since starting in Finland, it has been used in over 60
countries around the world. It was designed as a replacement
for the "talk" program but has become much much more than
that. IRC is a multi-user chat system, where people convene
on "channels" (a virtual place, usually with a topic of
conversation) to talk in groups, or privately. IRC is
constantly evolving, so the way things to work one week may
not be the way they work the next.
Good, what is IRCDOOR?
IRCDOOR/2 is an advanced 32-bit OS/2 Internet Relay Chat
client with main purpose of being able to be run from a BBS
(Bulletin Board System) as an external door program, that
would allow BBS users to IRC. Yes, it means that you could
*dramatically* increase your BBS popularity by adding IRC
service for your BBS users. Imagine a user who finds out
that something is much bigger, better and cooler than
a simple chat on BBS! Imagine a user who opens your Internet
service menu and starts a chat session on the Internet!
The following is a brief list of features that are supported
in current version of IRCDOOR/2:
-- natural 32-bit application capable of running simultaneously
at as many lines as you wish to register it for
-- as a BBS door supports TTY/ANSI interface
-- supports DORINFO1/DOORSYS drop-file formats
-- supports most standard IRCII 2.8 commands plus some
additional /CTCP-request commands and some specific
to IRCDOOR-only commands eg: /WHOELSE, /TIMELEFT, etc.
-- easy to setup (most options can be specified via command
line)
-- can be run in local mode too as a normal IRC client program
-- runs from any native OS/2 BBS that supports "hot" (open)
com port handles
-- flexible configuration
-- extensive Maximus BBS support (MEX code provided)
-- custom colors and other settings through config file
-- ability to be run from a DOS BBS (use Spawn program)
2. Software and Hardware requirements
Requires IBM PC (80486 is recommended), Internet connection
via ethernet, SLIP/PPP etc., IBM OS/2 version 2.0 or 3.0 and
IBM IAK (Internet Access Kit) with 32-bit TCP/IP libraries
(files: TCP32DLL.DLL and and SO32DLL.DLL). The Ray Gwinn's
SIO FOSSIL driver is also recommended for better perfomance.
SIO is also necessary if you are going to run IRCDOOR from
a DOS based BBS.
3. License agreement
IRCDOOR/2 IS COPYRIGHT AND PROPERTY OF ANDREW EIGUS, AN
INDEPENDENT SOFTWARE DEVELOPER (FREELANCER). NONE OF THE
PORTIONS CONTAINED IN THE IRCDOOR/2 DISTRIBUTION PACKAGE CAN
BE RESELLED, MODIFIED, DISASSEMBLED OR REPRODUCED IN ANY WAY
WITHOUT THE AUTHOR'S PERMISSION. PERMISSION IS GRANTED TO
ANYONE TO DISTRIBUTE THE ENTIRE PACKAGE IN THE NON-MODIFIED
FORM, PROVIDED THAT ALL FILES ARE KEPT IN THE DISTRIBUTION
ARCHIVE.
IRCDOOR/2 IS NEITHER PUBLIC DOMAIN, NOR FREEWARE. IRCDOOR IS
SHAREWARE SOFTWARE. YOU MAY EVALUATE IT FOR A TRIAL PERIOD OF
28 DAYS, AND THEN WHETHER REGISTER, OR DISCONTINUE USING IT.
4. Disclaimer
THIS SOFTWARE PROVIDED "AS-IS", WHICH MEANS THAT THERE IS
ABSOLUTELY NO WARRANTY PROVIDED BY THE AUTHOR. IN NO EVENT
THE AUTHOR WILL BE LIABLE TO YOU FOR ANY DAMAGES ARISING OUT
OF THE USE OF ANY PART OF THIS PROGRAM.
5. Installation instructions
Installation instructions are sub-divided in three sections.
Section 5.1 describes the door installation details for non-
Maximus BBS users, section 5.2 describes door installation
instructions for Maximus BBS, and sysops who are running a
DOS-based BBS under OS/2 should read sesction 5.3.
5.1 Installation for non-Maximus OS/2 BBS systems
a) Create an empty subdirectory in your BBS [doors]
directory called IRCDOOR. Let's say i am using Lora BBS,
and a path to my door games is C:\LORA\DOORS\, so i
create a directory C:\LORA\DOORS\IRCDOOR.
b) Unzip the distribution IRCDOOR archive to that directory,
so it would contain AT LEAST the following files:
IRCDOOR.EXE
IRCDOOR.CFG
IRCDOOR.HLP
c) Next, set up your BBS software for this door to be run; use
either DOOR.SYS (recommended) or DORINFO?.DEF format drop-
file. It should be created prior to running IRCDOOR by your
BBS software (see your BBS manual for details). Your BBS
software might be able to pass some information to IRCDOOR
via command-line: IRC server name, port number, etc. Even
some parameters in the drop-file can be overriden through
a command-line. See command-line switches in the Comments
section for more information about IRCDOOR/2 command line
parameters.
Your BBS software MUST be able to pass an open com port
"handle" parameter to IRCDOOR. IRCDOOR will NOT work in
the remote mode without port handle and BBS drop file path
specified as command-line arguments. (see -p and -d options
in the command line parameters paragraph). I recommend you
to create an OS/2 command file, for example IRCDOOR.CMD,
that will run the door. Here is sample command file:
@echo off
cd \lora\doors\ircdoor
if "%1"=="" goto local
if "%1"=="0" goto local
:remote
rem *** change the path below to specify a path to YOUR
rem *** drop file. In multinode environments, this usually
rem *** depends on a node number.
ircdoor -p%1 -dc:\lora\node%2\door.sys -k%2 -sirc.funet.fi -$6666
goto quit
:local
ircdoor -l -uSysOp -nSysOp -r"My Name" -sirc.funet.fi $6666
goto quit
:quit
cd \lora
This small command file above will do the job. It requires
two arguments: 1 - "hot" com port handle and 2 - BBS node
number. The node number will be used to specify a target
directory (path) for/to a drop file. IRCDOOR will automatically
determine drop file type by it's name. See command line
switches for more information.
d) Edit your STARTUP.CMD file in your system root directory
and add there the following line:
erase c:\ircdoor_home_directory\nodeinfo.* >nul
This command will erase old node information files from the
IRCDOOR home directory. Ircdoor_home_directory must be
replaced with the directory name where IRCDOOR/2 files are
located.
IRCDOOR/2 creates and uses nodeinfo.* files in it's home
directory and it automatically deletes them when a user
exits the door. But if you encounter a system crash during
the time when IRCDOOR is running, you should manually
remove nodeinfo.* files from it's home directory to prevent
IRCDOOR from thinking that it is running at the moment.
That's why the best way to avoid this is to insert that
mentioned erase command above to your STARTUP.CMD file so
whenever your system reboots, old IRCDOOR node information
files will be deleted.
There are many different types of BBS software for OS/2, and
most support passing various parameters via command line, and
most are able to write standard BBS drop-files (DOOR.SYS or
DORINFO?.DEF). If this is not your case, and you are
experiencing problems on how to setup a door, please contact
me at the address given at the bottom of this document. If
you own a DOS BBS, please see paragraph 5.3, which describes
how to setup IRCDOOR